-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
DataDog: Check for response object before returning the generic error #4259
Conversation
Signed-off-by: Ara Pulido <ara.pulido@datadoghq.com>
Signed-off-by: Ara Pulido <ara.pulido@datadoghq.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
CHANGELOG.md
Outdated
@@ -82,6 +82,7 @@ Here is an overview of all new **experimental** features: | |||
- **Kafka Scaler**: Support 0 in activationLagThreshold configuration ([#4137](https://github.com/kedacore/keda/issues/4137)) | |||
- **Prometheus Metrics**: Expose Prometheus Metrics also when getting ScaledObject state ([#4075](https://github.com/kedacore/keda/issues/4075)) | |||
- **Redis Scalers**: Fix panic produced by incorrect logger initialization ([#4197](https://github.com/kedacore/keda/issues/4197)) | |||
- **Datadog Scaler**: Return correct error when getting a 429 error ([#4187](https://github.com/kedacore/keda/issues/4187)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just a nit, could you please sort this alphabetically?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done!
/run-e2e datadog* |
Thanks for the fix @arapulido ! |
The Datadog API now creates a generic error object when returning a 429.
This fix checks the response object before the error object to craft a more complete error when reaching too many requests.
Checklist
- [ ] When introducing a new scaler, I agree with the scaling governance policy- [ ] I have verified that my change is according to the deprecations & breaking changes policy- [ ] Tests have been added- [ ] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)- [ ] A PR is opened to update the documentation on (repo) (if applicable)Fixes #4187